Position Or Builder
Functions
Link copied to clipboard
In meters above MSL (but see issue #359)
Content copied to clipboard
optional int32 altitude = 3;
Link copied to clipboard
Geoidal separation in meters
Content copied to clipboard
optional sint32 altitude_geoidal_separation = 10;
Link copied to clipboard
HAE altitude in meters - can be used instead of MSL altitude
Content copied to clipboard
optional sint32 altitude_hae = 9;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
.meshtastic.Position.AltSource altitude_source = 6;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
.meshtastic.Position.AltSource altitude_source = 6;
Link copied to clipboard
GPS fix quality (from NMEA GxGGA statement or similar)
Content copied to clipboard
uint32 fix_quality = 17;
Link copied to clipboard
GPS fix type 2D/3D (from NMEA GxGSA statement)
Content copied to clipboard
uint32 fix_type = 18;
Link copied to clipboard
GPS accuracy (a hardware specific constant) in mm
multiplied with DOP to calculate positional accuracy
Default: "'bout three meters-ish" :)
Content copied to clipboard
uint32 gps_accuracy = 14;
Link copied to clipboard
Ground speed in m/s and True North TRACK in 1/100 degrees
Clarification of terms:
- "track" is the direction of motion (measured in horizontal plane)
- "heading" is where the fuselage points (measured in horizontal plane)
- "yaw" indicates a relative rotation about the vertical axis
TODO: REMOVE/INTEGRATE
Content copied to clipboard
optional uint32 ground_speed = 15;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
optional uint32 ground_track = 16;
Link copied to clipboard
The new preferred location encoding, multiply by 1e-7 to get degrees
in floating point
Content copied to clipboard
optional sfixed32 latitude_i = 1;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
.meshtastic.Position.LocSource location_source = 5;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
.meshtastic.Position.LocSource location_source = 5;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
optional sfixed32 longitude_i = 2;
Link copied to clipboard
Estimated/expected time (in seconds) until next update:
- if we update at fixed intervals of X seconds, use X
- if we update at dynamic intervals (based on relative movement etc),
but "AT LEAST every Y seconds", use Y
Content copied to clipboard
uint32 next_update = 21;
Link copied to clipboard
Horizontal, Vertical and Position Dilution of Precision, in 1/100 units
- PDOP is sufficient for most cases
- for higher precision scenarios, HDOP and VDOP can be used instead,
in which case PDOP becomes redundant (PDOP=sqrt(HDOP^2 + VDOP^2))
TODO: REMOVE/INTEGRATE
Content copied to clipboard
uint32 PDOP = 11;
Link copied to clipboard
Indicates the bits of precision set by the sending node
Content copied to clipboard
uint32 precision_bits = 23;
Link copied to clipboard
GPS "Satellites in View" number
Content copied to clipboard
uint32 sats_in_view = 19;
Link copied to clipboard
Sensor ID - in case multiple positioning sensors are being used
Content copied to clipboard
uint32 sensor_id = 20;
Link copied to clipboard
A sequence number, incremented with each Position message to help
detect lost updates if needed
Content copied to clipboard
uint32 seq_number = 22;
Link copied to clipboard
This is usually not sent over the mesh (to save space), but it is sent
from the phone so that the local device can set its time if it is sent over
the mesh (because there are devices on the mesh without GPS or RTC).
seconds since 1970
Content copied to clipboard
fixed32 time = 4;
Link copied to clipboard
Positional timestamp (actual timestamp of GPS solution) in integer epoch seconds
Content copied to clipboard
fixed32 timestamp = 7;
Link copied to clipboard
Pos. timestamp milliseconds adjustment (rarely available or required)
Content copied to clipboard
int32 timestamp_millis_adjust = 8;
Link copied to clipboard
In meters above MSL (but see issue #359)
Content copied to clipboard
optional int32 altitude = 3;
Link copied to clipboard
Geoidal separation in meters
Content copied to clipboard
optional sint32 altitude_geoidal_separation = 10;
Link copied to clipboard
HAE altitude in meters - can be used instead of MSL altitude
Content copied to clipboard
optional sint32 altitude_hae = 9;
Link copied to clipboard
Ground speed in m/s and True North TRACK in 1/100 degrees
Clarification of terms:
- "track" is the direction of motion (measured in horizontal plane)
- "heading" is where the fuselage points (measured in horizontal plane)
- "yaw" indicates a relative rotation about the vertical axis
TODO: REMOVE/INTEGRATE
Content copied to clipboard
optional uint32 ground_speed = 15;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
optional uint32 ground_track = 16;
Link copied to clipboard
The new preferred location encoding, multiply by 1e-7 to get degrees
in floating point
Content copied to clipboard
optional sfixed32 latitude_i = 1;
Link copied to clipboard
TODO: REPLACE
Content copied to clipboard
optional sfixed32 longitude_i = 2;